Move test_podman_login_check to destructive tests - #20849
Conversation
Reviewer's guide (collapsed on small PRs)Reviewer's GuideAdjusts the podman login test finalizer so that it restores a logged-in state instead of leaving the host logged out, preventing subsequent tests from failing due to missing registry authentication. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
3c0ce6f to
594358a
Compare
594358a to
9768556
Compare
|
|
PRT Result |
9768556 to
629fbd8
Compare
|
|
|
trigger: test-robottelo |
|
trigger: test-robottelo |
|
PRT Result |
|
Removing |
|
Adding test |
|
ef465e2 to
9daa4b1
Compare
|
PRT Result |
|
4c0d98a to
7c492e4
Compare
|
|
PRT Result |
|
All tests have passed. |
7c492e4 to
1c26b83
Compare
|
|
PRT Result |
|
trigger: test-robottelo |
|
PRT Result |
|
Required testcases are passed. |
1c26b83 to
d4b1266
Compare
d4b1266 to
f26efe4
Compare
(cherry picked from commit 5deb533)
Problem Statement
On an IoP-enabled Satellite, test_podman_login_check logs out of the container registry at the end of the test and uses a finalizer that also calls podman_logout. That leaves the host in a logged-out state. Other tests that run on the same host (e.g. test_positive_health_check_pre_upgrade when the “satellite” host is IoP) then run pre-upgrade health checks that include “Check whether podman needs to be logged in to the registry,” and those checks fail because podman is still logged out.
Solution
Move the test_podman_login_check to destructive so other test are successfully run
Related Issues
Summary by Sourcery
Bug Fixes: